home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20020314-20021006
/
000390_fdc@columbia.edu_Wed Sep 25 09:24:31 EDT 2002.msg
< prev
next >
Wrap
Text File
|
2020-01-01
|
6KB
|
148 lines
Article: 13726 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!news.columbia.edu!news-not-for-mail
From: fdc@columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc,comp.unix.xenix.sco,comp.dcom.modems
Subject: Re: Help! Trying to send files via serial modem...
Date: 25 Sep 2002 09:24:19 -0400
Organization: Columbia University
Lines: 131
Message-ID: <amsde3$d5d$1@watsol.cc.columbia.edu>
References: <7ea6ad1.0209241717.7af4adc8@posting.google.com>
NNTP-Posting-Host: watsol.cc.columbia.edu
X-Trace: newsmaster.cc.columbia.edu 1032960260 25217 128.59.39.139 (25 Sep 2002 13:24:20 GMT)
X-Complaints-To: postmaster@columbia.edu
NNTP-Posting-Date: 25 Sep 2002 13:24:20 GMT
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:13726 comp.unix.xenix.sco:18667 comp.dcom.modems:316229
In article <7ea6ad1.0209241717.7af4adc8@posting.google.com>,
Ray Ward <rayward@metronet.com> wrote:
: What I'm trying to do:
: New federal legislation requires financial institutions to check
: certain transactions against a federal database of suspected
: terrorists. To do this, my client needs to get data off of a fairly
: large number (100's) of old Xenix 2.3.2 SysV boxes (i386) to an
: off-site, modern box to do the checking. (I'm not sure that all the
: Xenix boxes are the exact same version.) Deadline's in October.
:
: My first thought was to automatically send files daily using Kermit
: from a cron(1) script to a ProCommPlus 4.8 server running in Kermit
: server mode on the client's Win2000 box.
:
: The Xenix boxes have only a
: 1.2Mb 5.25 floppy and a serial port external US Robotics Sportster
: modem (ranging from 2400-14400 bps). They were bought with
: application software only, no C compiler, make, man, etc..
:
OK, too bad, no building modern Kermit versions. But maybe other readers
can help there.
: ...so I have to find an executable file.
:
We have the following SCO Xenix binaries on our FTP site:
cku192.sco286 Xenix/286 2.2.1
cku190b02.sco386netc-2.2.3 Xenix/386 2.2.3
cku192.sco3r2lai Xenix/386 2.3.3 with Lachman Assoc TCP/IP
cku201.sco234 Xenix/386 2.3.4
Plus some other 2.3.4 variations. You can find them here:
http://www.columbia.edu/kermit/ck80binaries.html
All of these except the 2.3.4 ones are rather old (C-Kermit version 5 or 6)
but still much newer than the one you have (version 4).
: They already have the ProCommPlus set up.
:
: When I try to connect from the interactive Kermit that I found on one
: machine (072 24 Jan 89 Xenix/286) it seems to connect...
:
Could I get you to upload that binary to our site so we can include it
with the other Xenix binaries?
ftp://kermit.columbia.edu/kermit/incoming/
, then drops the
: line. I tried loading the G-Kermit binary from the Columbia site, but
: it's not interactive, and I can't figure out how to get it to dial
: before trying to send the files.
:
I suspect you're going about this backwards, but more about this later...
: So, I downloaded the 21-day eval copy of Kermit95 2.0 onto my Win98
: box and got the same result, with a little more detail:
:
: Kermit session.log:
: ATQ0V1
:
: OK
: ATDT9721234567
:
: CONNECT
: (see garbage...)
: NO CARRIER
:
: Looks kind of like a baud rate mismatch. So I set both the PC+ and
: the Kermit95 to 2400 baud, xon/xoff, 8n1, full duples, 1 check byte.
: Didn't help.
:
Let's assume your plan is to dial each Xenix box from Windows, log in,
start Kermit on Xenix, then transfer the file (since having 100 Xenix
boxes call one Windows box would not make a lot of sense).
The Windows box no doubt has an all-singing all-dancing V.Everything modem,
most likely a Winmodem. The first thing you need to know about these is
that you must address them by the Windows name (from the Modems folder in
the Control Panel), not by their DOS name, such as COM1. In Kermit 95:
set port tapi
set speed xxxx
dial 9721234567
But "xxxx" is the kicker. What should it be? Does the calling modem
support protocol negotiation and fallback? If not, you'll need to set K95's
interface speed to whatever each Xenix modem supports. If the Xenix modem
is V.32 or higher, it shouldn't matter -- the two modems will negotiate a
usable connection and the calling modem can do "speed buffering". But of
course, the answering modem must still be configured to use an interface
speed that agrees with what Xenix getty/login expect. Or you can try
sending a BREAK signal (Alt-B in Kermit 95) to see if it will make Xenix
login change its speed (try this up to 15 times).
If you really do have 2400 bps answering modems, then you'll need to dumb
down the calling modem like so:
set port tapi
set speed 2400
set modem error-correction off
set modem data-compression off
set modem speed-matching off
because otherwise the negotiations sent by the calling modem will confuse
the answering modem (or Xenix login) so much that you'll have to hang
up anyway.
If all the Xenix boxes are different, then getting this to work 100 times
might be tricky, and in that case maybe it DOES make sense to have the
Xenixes call Windows after all. But then you have a couple new problems:
1. Windows is not like Xenix -- you can't call it up, get a login:
prompt, log in, and run programs. You have to set Kermit 95 on
Xenix up to wait for incoming calls, answer them, and then enter
server mode or something.
2. You'll no doubt have contention, so your calling procedure will have
handle the busy-redial scenario (which modern C-Kermit programs are
fully capable of, but not the ancient one you have).
Anyway, as to problem (1), see:
http://www.columbia.edu/kermit/k95.html#modems
If you can get a more modern version of Kermit to run on Xenix, then you
can script everything:
http://www.columbia.edu/kermit/ckscripts.html
- Frank